Automation of a process running in a first session via a robotic process automation robot running in a second session

ABSTRACT

Automation of a process running in a first session via robotic process automation (RPA) robot(s) running in a second session is disclosed. In some aspects, a form is displayed in a user session, but one or more attended RPA robots that retrieve and/or interact with data for an application in the first session run in one or more other sessions. In this manner, the operation of the RPA robot(s) may not prevent the user from using other applications or instances when the RPA robot(s) are running, but the data modifications made or facilitated by the RPA robot(s) may be visible to the user in the first session window.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Nonprovisional patentapplication Ser. No. 16/925,544 filed Jul. 10, 2020, which is acontinuation of U.S. Nonprovisional patent application Ser. No.16/924,910 filed Jul. 9, 2020. The subject matter of these earlier filedapplications is hereby incorporated by reference in its entirety.

FIELD

The present invention generally relates to robotic process automation(RPA), and more specifically, to automation of a process running in afirst session via RPA robot(s) running in a second session.

BACKGROUND

Attended automation RPA robots, for example, typically run on acomputing system operated by a user in the same session as that user.The RPA robots may work with a user to accomplish certain tasks at auser's command, for example. However, in attended automation scenarios,the RPA robot may “take over” the user's computing system. The user maywish to perform other activities while the robot is interacting with thecomputing system, but the user is prevented from doing so. In otherwords, the robot controls applications through the user interface (UI)in the same manner that the user would (e.g., simulating mouse clicksand keyboard input).

Various technologies exist that create complete or partial copies of anoperating system or the applications running thereon. Emulators havebeen around for decades and may provide developers with the ability totest and debug applications. For instance, emulators may providedevelopers with the ability to test and debug mobile applications thatuse an operating system that does not support running development toolsdirectly. Both Android® and iOS® offer emulators that can be run from adevelopment machine to test and debug an Android® or iOS® applicationsince the developer tools cannot be natively run on those mobileoperating systems.

Simulators allow a developer to host a window on his or her localmachine that lets the developer test and debug behavior of anapplication that are difficult or impossible to perform on a developmentmachine. For example, simulators allow the developer to click a buttonto rotate the simulator, which tells the application running inside thesimulator the device has been rotated for the purposes of testing anddebugging application behavior that responds to these events. Anothercommon example is multi-touch. Many developer machines do not supporttouch, so the simulator lets the developer test and debug how theapplication responds to multiple touch points. Android® and iOS®emulators also offer simulation capabilities. Furthermore, Microsoft®offers a simulator for their Universal Windows Platform (UWP)applications.

Virtual machines host a second operating system on the machine and canbe opened and monitored through a window. This runs a completelydifferent operating system and shares the hardware with the hostmachine. The “guest” machine must have its own copies of applicationsinstalled and does not share common resources or files with the usermachine.

Docker® containers are conceptually a hybrid form of virtual machine.All of the applications that need to be executed are packaged into animmutable package that is executed directly on the host operatingsystem. The package is not a complete copy of another operating system,but it does not by default share or have access to any of theapplications or resources on the host machine. Thus, from a userexperience perspective, Docker® containers feel similar to a virtualmachine, but technically, the containers are not executing on acompletely separate operating system.

However, conventional emulators, simulators, virtual machines (VMs), andhybrid VMs providing operating system (OS)-level virtualization (e.g.,Docker® containers) do not address the issues that arise with attendedautomation robots operating on the same computing system as the user.Thus, the user essentially becomes a spectator for his or her owncomputing system, watching the robot work and being unable to interactwith other applications on the machine that require user interaction.Accordingly, an improved approach may be beneficial.

SUMMARY

Certain embodiments of the present invention may provide solutions tothe problems and needs in the art that have not yet been fullyidentified, appreciated, or solved by current RPA technologies. Forexample, some embodiments of the present invention pertain to automationof a process running in a first session via RPA robot(s) running in asecond session.

In an embodiment, a computer program is embodied on a non-transitorycomputer-readable medium. The computer program is configured to cause atleast one processor to execute an inter-process communication (IPC)facilitator and an RPA driver in a first session and execute an RPArobot in a second session. The computer program is also configured tocause the at least one processor to receive one or more messages fromthe RPA robot via IPC, by the IPC facilitator, and control the RPAdriver to interact with an application or application object running inthe first session, by the IPC facilitator, based on the received one ormore messages from the RPA robot.

In another embodiment, a computer-implemented method includes sendingone or more messages to an IPC facilitator running in a first sessionvia IPC, by an RPA robot running in a second session, and receiving oneor more messages from the RPA robot via IPC, by the IPC facilitator. Thecomputer-implemented method also includes controlling an RPA driverrunning in the first session to interact with an application orapplication object also running in the first session, by the IPCfacilitator, based on the received one or more messages from the RPArobot.

In yet another embodiment, a computer-implemented method includesreceiving one or more messages from an RPA robot running in a secondsession via IPC, by an IPC facilitator running in a first session. Thecomputer-implemented method also includes controlling an RPA driverrunning in the first session to interact with an application orapplication object also running in the first session, by the IPCfacilitator, based on the received one or more messages from the RPArobot.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of certain embodiments of the inventionwill be readily understood, a more particular description of theinvention briefly described above will be rendered by reference tospecific embodiments that are illustrated in the appended drawings.While it should be understood that these drawings depict only typicalembodiments of the invention and are not therefore to be considered tobe limiting of its scope, the invention will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is an architectural diagram illustrating a robotic processautomation (RPA) system, according to an embodiment of the presentinvention.

FIG. 2 is an architectural diagram illustrating a deployed RPA system,according to an embodiment of the present invention.

FIG. 3 is an architectural diagram illustrating the relationship betweena designer, activities, and drivers, according to an embodiment of thepresent invention.

FIG. 4 is an architectural diagram illustrating an RPA system, accordingto an embodiment of the present invention.

FIG. 5 is an architectural diagram illustrating a computing systemconfigured to facilitate inter-session automation for RPA robots,according to an embodiment of the present invention.

FIGS. 6A-G illustrate an example of completing a form in a user sessionusing an RPA robot running in a robot session, an IPC facilitator, andan RPA driver, according to an embodiment of the present invention.

FIGS. 7A-G illustrate an example of completing a form in a user sessionusing an RPA robot running in a robot session via direct variablemodification, according to an embodiment of the present invention.

FIG. 8 is a flowchart illustrating a process for automation of a processrunning in a user session via an RPA robot running in a robot session,an IPC facilitator, and an RPA driver, according to an embodiment of thepresent invention.

FIG. 9 is a flowchart illustrating a process for automation of a processrunning in a user session via an RPA robot running in a robot sessionvia direct variable modification, according to an embodiment of thepresent invention.

FIG. 10 illustrates an example of multiple client session RPA robotsinteracting with a main session application, according to an embodimentof the present invention.

FIG. 11 is a flow diagram illustrating a process for running an attendedautomation RPA robot in a client session, according to an embodiment ofthe present invention.

FIG. 12 is a flow diagram illustrating execution of a multi-robotcollective workflow between a main session robot M1, a client sessionapplication A1, and a pair of client session robots C1 and C2, accordingto an embodiment of the present invention.

FIG. 13 is a flow diagram illustrating execution of a main session RPArobot and a client session RPA robot in parallel, according to anembodiment of the present invention.

FIG. 14 is a flow diagram illustrating execution of a client session RPArobot based on a trigger for a main session application, according to anembodiment of the present invention.

FIG. 15 is a flowchart illustrating a process for performinginter-session automation, according to an embodiment of the presentinvention.

Unless otherwise indicated, similar reference characters denotecorresponding features consistently throughout the attached drawings.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Some embodiments pertain to automation of a process running in a firstsession via RPA robot(s) running in a second session. For instance, aform (e.g., a web page, an email application (e.g., Outlook®), aspreadsheet application (e.g., Excel®), a customer relationshipmanagement (CRM) system application (e.g., Salesforce®), an enterpriseresource management (ERM) system, a supply chain management system, acustom-built computer application, a mobile application, anotherapplication having fillable fields, etc.) may be displayed in a firstsession. In some embodiments, the first session may be a user session(also called a main session or a parent session herein). One or more RPArobots that retrieve and/or interact with data for an application in thefirst session may run in one or more other sessions (also called robotsessions, second sessions, or secondary sessions herein). In certainembodiments, the robot session may be a child session of the firstsession.

In some embodiments, the RPA robot running in the client session sendsmessages to an RPA driver running in the main session via inter-processcommunication (IPC). Based on the IPC communication(s) from the RPArobot, the RPA driver may implement various operating system (OS) and/orapplication programming interface (API)-level interactions with acomputing system. For instance, the driver may move the mouse, click abutton, interact with a menu, enter text in a field, open or close awindow, move and/or resize a window, or perform any other suitableinteraction without deviating from the scope of the invention.

In order to implement this functionality, the driver may include or becontrolled or called by an IPC facilitator. The IPC facilitator may be aseparate application or process, or may be a subprocess of the driver insome embodiments. The IPC facilitator may listen for IPC messages fromthe RPA robot in the client session (e.g., listen for a trigger), sendcommunications to and receive communications from the RPA robot, monitorRPA robot execution status, a combination thereof, etc. The IPCfacilitator may also cause the driver to implement the desiredfunctionality in the parent session based on the IPC communication(s)from the RPA robot. In certain embodiments, the IPC facilitator may beconfigured with a script for a given RPA robot. In some embodiments, theIPC facilitator may be custom designed for the functionality to beperformed in the parent session.

In some embodiments, the RPA robot in the client session may directlymodify variables stored in memory on a computing system. An applicationrunning in the parent session that accesses these variables could thenupdate displayed values when the display refreshes or the applicationotherwise reloads its UI. For example, variables of an Excel®spreadsheet could be modified directly by the RPA robot running in theclient session, which would change the values displayed in the parentsession as well.

In some embodiments, the operation of the RPA robot(s) may not preventthe user from using other applications or instances when the RPA robotis running, but the data modifications made by the RPA robot(s) may bevisible to the user as the application display refreshes in the usersession window. However, in certain embodiments, the RPA robot(s) mayinteract with applications that do not have a user interface.

In some embodiments, the process may operate as follows. A user mayclick a button or otherwise cause an RPA robot to launch in a childsession of the user session (e.g., the parent or main session that islaunched when the user boots up his or her computing system). In certainembodiments, the robot session may already be running, or may beseparately launched by the user from a robot tray, for example. The usermay cause the robot to execute its workflow in the child session, andthe robot may then interact with one or more applications in the mainsession by communicating with an IPC facilitator running in the parentsession. The IPC facilitator may then cause an RPA driver to carry outthe desired functionality in the parent session.

In some embodiments, the RPA robot running in the robot session maypause operation and provide a message if at least one application whichthe workflow pertains to has not been launched, and the IPC facilitatormay launch the application so the robot can continue operation. Once therobot begins executing its workflow, changes to displayed data in theapplication may be visible in the main session window when such changesare made via the IPC facilitator and RPA driver. For instance, data mayappear as the driver fills the data in based on data provided by the RPArobot in the client session (e.g., via IPC, saving data in a flat fileor database, etc.).

By way of nonlimiting example, in some embodiments, a shortcut may becreated in Salesforce® that causes an RPA robot to launch in a clientsession, or interacts with an already running RPA robot in the clientsession. When a user clicks the shortcut, the RPA robot begins executingan RPA process as designed in its RPA workflow. Based on the results ofits execution (e.g., retrieving information from a database, calling anartificial intelligence (AI)/machine learning (ML) model and obtainingresults, obtaining information from multiple legacy systems, etc.), theRPA robot then interacts with an IPC facilitator, which then interactsaccordingly with a running Salesforce® application instance in theparent session. This may cause some of the displayed information in therunning Salesforce® application instance to change and be visible to theuser, for example, as the RPA driver performs the interactions.

In certain embodiments, the RPA robot running in the client session maycause an application in the parent session to open via the IPCfacilitator. The IPC facilitator, via the RPA driver, may then accessthe data associated with the application and make additions, changes,and/or deletions. In this manner, even though the RPA robot is notrunning in the parent session, the RPA robot is still able to causeinteractions in the parent session applications in a manner that appearssimilar to a RPA robot running in the parent session itself, but isfunctionally different.

In some embodiments, a user may cause a robot to execute a workflow inthe client session that goes to a website and collects some information.The RPA robot may then provide this information to an IPC facilitator,which then causes an RPA driver to enter the collected information in aspreadsheet that is visible in the main session, for example. In certainembodiments, an application, such as Salesforce®, is open in the mainsession. The user then runs an automation in the client session thatreads the current client ID, goes to a website (e.g., HubSpot®), andcollects information pertaining to client interactions with the website,for example. However, attended RPA robots may interact with any suitableapplication(s) via the RPA facilitator and/or may obtain data from anysuitable source (e.g., a database, another application, etc.) withoutdeviating from the scope of the invention.

Applications of some embodiments include, but are not limited to,emulators, simulators, VMs, and hybrid VMs providing OS-levelvirtualization (e.g., Docker® containers). Some embodiments create andhost one or more robot sessions as a window including the UIs ofapplications being controlled by an attended automation process. Incertain embodiments, only the interfaces of applications with which therobot(s) interact are shown. In some embodiments, no client sessionwindow is shown at all. As used herein, a “window” may apply to a windowrepresenting a UI shown within the main UI, a second screen of a seconddisplay of a computing system, a virtual desktop, an isolatedenvironment (i.e., a window (referred to as the “host”) that draws theUIs of all applications launched inside the environment (referred to as“children”) and runs them in the context of the host session), etc.without deviating from the scope of the invention. Running multiplesessions allows robot(s) to operate in their session(s) while the userinteracts with a first session (e.g., a parent session). The user maythus be able to interact with various applications while the robotinteracts with the data thereof.

In some embodiments, any desired number of sessions for any number ofrobots may be created and used without deviating from the scope of theinvention. For instance, a user may operate in a first session, a firstrobot may operate in a second session, a second robot may operate in athird session, etc. In certain embodiments, multiple robots may operatein a single session, potentially taking turns for interacting with oneor more common applications via the RPA facilitator.

The functionality for creating the session may be implemented viaWindows® Terminal Services Child Sessions, for example, which can createa session back into a user's own machine without the user having to logout. The newly created session appears as a child window and containsand launches applications that exist in the user's session. In otherwords, the separation between the user and the robot occurs at the UIlevel. If a file is deleted, for example, this occurs across allsessions running on the computing system.

Certain embodiments may be employed for robotic process automation(RPA). FIG. 1 is an architectural diagram illustrating an RPA system100, according to an embodiment of the present invention. RPA system 100includes a designer 110 that allows a developer to design and implementworkflows. Designer 110 may provide a solution for applicationintegration, as well as automating third-party applications,administrative Information Technology (IT) tasks, and business ITprocesses. Designer 110 may facilitate development of an automationproject, which is a graphical representation of a business process.Simply put, designer 110 facilitates the development and deployment ofworkflows and robots.

The automation project enables automation of rule-based processes bygiving the developer control of the execution order and the relationshipbetween a custom set of steps developed in a workflow, defined herein as“activities.” One commercial example of an embodiment of designer 110 isUiPath Studio™. Each activity may include an action, such as clicking abutton, reading a file, writing to a log panel, etc. In someembodiments, workflows may be nested or embedded.

Some types of workflows may include, but are not limited to, sequences,flowcharts, FSMs, and/or global exception handlers. Sequences may beparticularly suitable for linear processes, enabling flow from oneactivity to another without cluttering a workflow. Flowcharts may beparticularly suitable to more complex business logic, enablingintegration of decisions and connection of activities in a more diversemanner through multiple branching logic operators. FSMs may beparticularly suitable for large workflows. FSMs may use a finite numberof states in their execution, which are triggered by a condition (i.e.,transition) or an activity. Global exception handlers may beparticularly suitable for determining workflow behavior whenencountering an execution error and for debugging processes.

Once a workflow is developed in designer 110, execution of businessprocesses is orchestrated by conductor 120, which orchestrates one ormore robots 130 that execute the workflows developed in designer 110.One commercial example of an embodiment of conductor 120 is UiPathOrchestrator™. Conductor 120 facilitates management of the creation,monitoring, and deployment of resources in an environment. Conductor 120may act as an integration point, or one of the aggregation points, withthird-party solutions and applications.

Conductor 120 may manage a fleet of robots 130, connecting and executingrobots 130 from a centralized point. Types of robots 130 that may bemanaged include, but are not limited to, attended robots 132, unattendedrobots 134, development robots (similar to unattended robots 134, butused for development and testing purposes), and nonproduction robots(similar to attended robots 132, but used for development and testingpurposes). Attended robots 132 may be triggered by user events or bescheduled to automatically happen, and operate alongside a human on thesame computing system. Attended robots 132 may be used with conductor120 for a centralized process deployment and logging medium. Attendedrobots 132 may help the human user accomplish various tasks, and may betriggered by user events. In some embodiments, processes cannot bestarted from conductor 120 on this type of robot and/or they cannot rununder a locked screen. In certain embodiments, attended robots 132 canonly be started from a robot tray or from a command prompt. Attendedrobots 132 should run under human supervision in some embodiments.

Unattended robots 134 run unattended in virtual environments and canautomate many processes. Unattended robots 134 may be responsible forremote execution, monitoring, scheduling, and providing support for workqueues. Debugging for all robot types may be run from designer 110 insome embodiments. Both attended and unattended robots may automatevarious systems and applications including, but not limited to,mainframes, web applications, VMs, enterprise applications (e.g., thoseproduced by SAP®, SalesForce®, Oracle®, etc.), and computing systemapplications (e.g., desktop and laptop applications, mobile deviceapplications, wearable computer applications, etc.).

Conductor 120 may have various capabilities including, but not limitedto, provisioning, deployment, versioning, configuration, queueing,monitoring, logging, and/or providing interconnectivity. Provisioningmay include creating and maintenance of connections between robots 130and conductor 120 (e.g., a web application). Deployment may includeassuring the correct delivery of package versions to assigned robots 130for execution. Versioning may include management of unique instances ofsome process or configuration in some embodiments. Configuration mayinclude maintenance and delivery of robot environments and processconfigurations. Queueing may include providing management of queues andqueue items. Monitoring may include keeping track of robotidentification data and maintaining user permissions. Logging mayinclude storing and indexing logs to a database (e.g., an SQL database)and/or another storage mechanism (e.g., ElasticSearch®, which providesthe ability to store and quickly query large datasets). Conductor 120may provide interconnectivity by acting as the centralized point ofcommunication for third-party solutions and/or applications.

Robots 130 are execution agents that run workflows built in designer110. One commercial example of some embodiments of robot(s) 130 isUiPath Robots™. In some embodiments, robots 130 install the MicrosoftWindows® Service Control Manager (SCM)-managed service by default. As aresult, such robots 130 can open interactive Windows® sessions under thelocal system account, and have the rights of a Windows® service.

In some embodiments, robots 130 can be installed in a user mode. Forsuch robots 130, this means they have the same rights as the user underwhich a given robot 130 has been installed. This feature may also beavailable for High Density (HD) robots, which ensure full utilization ofeach machine at its maximum potential. In some embodiments, any type ofrobot 130 may be configured in an HD environment.

Robots 130 in some embodiments are split into several components, eachbeing dedicated to a particular automation task. The robot components insome embodiments include, but are not limited to, SCM-managed robotservices, user mode robot services, executors, agents, and command line.SCM-managed robot services manage and monitor Windows® sessions and actas a proxy between conductor 120 and the execution hosts (i.e., thecomputing systems on which robots 130 are executed). These services aretrusted with and manage the credentials for robots 130. A consoleapplication is launched by the SCM under the local system.

User mode robot services in some embodiments manage and monitor Windows®sessions and act as a proxy between conductor 120 and the executionhosts. User mode robot services may be trusted with and manage thecredentials for robots 130. A Windows® application may automatically belaunched if the SCM-managed robot service is not installed.

Executors may run given jobs under a Windows® session (i.e., they mayexecute workflows. Executors may be aware of per-monitor dots per inch(DPI) settings. Agents may be Windows® Presentation Foundation (WPF)applications that display the available jobs in the system tray window.Agents may be a client of the service. Agents may request to start orstop jobs and change settings. The command line is a client of theservice. The command line is a console application that can request tostart jobs and waits for their output.

Having components of robots 130 split as explained above helpsdevelopers, support users, and computing systems more easily run,identify, and track what each component is executing. Special behaviorsmay be configured per component this way, such as setting up differentfirewall rules for the executor and the service. The executor may alwaysbe aware of DPI settings per monitor in some embodiments. As a result,workflows may be executed at any DPI, regardless of the configuration ofthe computing system on which they were created. Projects from designer110 may also be independent of browser zoom level in some embodiments.For applications that are DPI-unaware or intentionally marked asunaware, DPI may be disabled in some embodiments.

FIG. 2 is an architectural diagram illustrating a deployed RPA system200, according to an embodiment of the present invention. In someembodiments, RPA system 200 may be, or may be a part of, RPA system 100of FIG. 1. It should be noted that the client side, the server side, orboth, may include any desired number of computing systems withoutdeviating from the scope of the invention. On the client side, a robotapplication 210 includes executors 212, an agent 214, and a designer216. However, in some embodiments, designer 216 may not be running oncomputing system 210. Executors 212 are running processes. Severalbusiness projects may run simultaneously, as shown in FIG. 2. Agent 214(e.g., a Windows® service) is the single point of contact for allexecutors 212 in this embodiment. All messages in this embodiment arelogged into conductor 230, which processes them further via databaseserver 240, indexer server 250, or both. As discussed above with respectto FIG. 1, executors 212 may be robot components.

In some embodiments, a robot represents an association between a machinename and a username. The robot may manage multiple executors at the sametime. On computing systems that support multiple interactive sessionsrunning simultaneously (e.g., Windows® Server 2012), multiple robots maybe running at the same time, each in a separate Windows® session using aunique username. This is referred to as HD robots above.

Agent 214 is also responsible for sending the status of the robot (e.g.,periodically sending a “heartbeat” message indicating that the robot isstill functioning) and downloading the required version of the packageto be executed. The communication between agent 214 and conductor 230 isalways initiated by agent 214 in some embodiments. In the notificationscenario, agent 214 may open a WebSocket channel that is later used byconductor 230 to send commands to the robot (e.g., start, stop, etc.).

On the server side, a presentation layer (web application 232, Open DataProtocol (OData) Representative State Transfer (REST) ApplicationProgramming Interface (API) endpoints 234, and notification andmonitoring 236), a service layer (API implementation/business logic238), and a persistence layer (database server 240 and indexer server250) are included. Conductor 230 includes web application 232, ODataREST API endpoints 234, notification and monitoring 236, and APIimplementation/business logic 238. In some embodiments, most actionsthat a user performs in the interface of conductor 230 (e.g., viabrowser 220) are performed by calling various APIs. Such actions mayinclude, but are not limited to, starting jobs on robots,adding/removing data in queues, scheduling jobs to run unattended, etc.without deviating from the scope of the invention. Web application 232is the visual layer of the server platform. In this embodiment, webapplication 232 uses Hypertext Markup Language (HTML) and JavaScript(JS). However, any desired markup languages, script languages, or anyother formats may be used without deviating from the scope of theinvention. The user interacts with web pages from web application 232via browser 220 in this embodiment in order to perform various actionsto control conductor 230. For instance, the user may create robotgroups, assign packages to the robots, analyze logs per robot and/or perprocess, start and stop robots, etc.

In addition to web application 232, conductor 230 also includes servicelayer that exposes OData REST API endpoints 234. However, otherendpoints may be included without deviating from the scope of theinvention. The REST API is consumed by both web application 232 andagent 214. Agent 214 is the supervisor of one or more robots on theclient computer in this embodiment.

The REST API in this embodiment covers configuration, logging,monitoring, and queueing functionality. The configuration endpoints maybe used to define and configure application users, permissions, robots,assets, releases, and environments in some embodiments. Logging RESTendpoints may be used to log different information, such as errors,explicit messages sent by the robots, and other environment-specificinformation, for instance. Deployment REST endpoints may be used by therobots to query the package version that should be executed if the startjob command is used in conductor 230. Queueing REST endpoints may beresponsible for queues and queue item management, such as adding data toa queue, obtaining a transaction from the queue, setting the status of atransaction, etc.

Monitoring REST endpoints may monitor web application 232 and agent 214.Notification and monitoring API 236 may be REST endpoints that are usedfor registering agent 214, delivering configuration settings to agent214, and for sending/receiving notifications from the server and agent214. Notification and monitoring API 236 may also use WebSocketcommunication in some embodiments.

The persistence layer includes a pair of servers in thisembodiment—database server 240 (e.g., a SQL server) and indexer server250. Database server 240 in this embodiment stores the configurations ofthe robots, robot groups, associated processes, users, roles, schedules,etc. This information is managed through web application 232 in someembodiments. Database server 240 may manages queues and queue items. Insome embodiments, database server 240 may store messages logged by therobots (in addition to or in lieu of indexer server 250).

Indexer server 250, which is optional in some embodiments, stores andindexes the information logged by the robots. In certain embodiments,indexer server 250 may be disabled through configuration settings. Insome embodiments, indexer server 250 uses ElasticSearch®, which is anopen source project full-text search engine. Messages logged by robots(e.g., using activities like log message or write line) may be sentthrough the logging REST endpoint(s) to indexer server 250, where theyare indexed for future utilization.

FIG. 3 is an architectural diagram illustrating the relationship 300between a designer 310, activities 320, 330, and drivers 340, accordingto an embodiment of the present invention. Per the above, a developeruses designer 310 to develop workflows that are executed by robots.Workflows may include user-defined activities 320 and UI automationactivities 330. Some embodiments are able to identify non-textual visualcomponents in an image, which is called computer vision (CV) herein.Some CV activities pertaining to such components may include, but arenot limited to, click, type, get text, hover, element exists, refreshscope, highlight, etc. Click in some embodiments identifies an elementusing CV, optical character recognition (OCR), fuzzy text matching, andmulti-anchor, for example, and clicks it. Type may identify an elementusing the above and types in the element. Get text may identify thelocation of specific text and scan it using OCR. Hover may identify anelement and hover over it. Element exists may check whether an elementexists on the screen using the techniques described above. In someembodiments, there may be hundreds or even thousands of activities thatcan be implemented in designer 310. However, any number and/or type ofactivities may be available without deviating from the scope of theinvention.

UI automation activities 330 are a subset of special, lower levelactivities that are written in lower level code (e.g., CV activities)and facilitate interactions with the screen. UI automation activities330 facilitate these interactions via drivers 340 that allow the robotto interact with the desired software. For instance, drivers 340 mayinclude OS drivers 342, browser drivers 344, VM drivers 346, enterpriseapplication drivers 348, etc.

Drivers 340 may interact with the OS at a low level looking for hooks,monitoring for keys, etc. They may facilitate integration with Chrome®,IE®, Citrix®, SAP®, etc. For instance, the “click” activity performs thesame role in these different applications via drivers 340.

FIG. 4 is an architectural diagram illustrating an RPA system 400,according to an embodiment of the present invention. In someembodiments, RPA system 400 may be or include RPA systems 100 and/or 200of FIGS. 1 and/or 2. RPA system 400 includes multiple client computingsystems 410 running robots. Computing systems 410 are able tocommunicate with a conductor computing system 420 via a web applicationrunning thereon. Conductor computing system 420, in turn, is able tocommunicate with a database server 430 and an optional indexer server440.

With respect to FIGS. 1 and 3, it should be noted that while a webapplication is used in these embodiments, any suitable client/serversoftware may be used without deviating from the scope of the invention.For instance, the conductor may run a server-side application thatcommunicates with non-web-based client software applications on theclient computing systems.

FIG. 5 is an architectural diagram illustrating a computing system 500configured to facilitate inter-session automation for RPA robots,according to an embodiment of the present invention. In someembodiments, computing system 500 may be one or more of the computingsystems depicted and/or described herein. Computing system 500 includesa bus 505 or other communication mechanism for communicatinginformation, and processor(s) 510 coupled to bus 505 for processinginformation. Processor(s) 510 may be any type of general or specificpurpose processor, including a Central Processing Unit (CPU), anApplication Specific Integrated Circuit (ASIC), a Field ProgrammableGate Array (FPGA), a Graphics Processing Unit (GPU), multiple instancesthereof, and/or any combination thereof. Processor(s) 510 may also havemultiple processing cores, and at least some of the cores may beconfigured to perform specific functions. Multi-parallel processing maybe used in some embodiments. In certain embodiments, at least one ofprocessor(s) 510 may be a neuromorphic circuit that includes processingelements that mimic biological neurons. In some embodiments,neuromorphic circuits may not require the typical components of a VonNeumann computing architecture.

Computing system 500 further includes a memory 515 for storinginformation and instructions to be executed by processor(s) 510. Memory515 can be comprised of any combination of Random Access Memory (RAM),Read Only Memory (ROM), flash memory, cache, static storage such as amagnetic or optical disk, or any other types of non-transitorycomputer-readable media or combinations thereof. Non-transitorycomputer-readable media may be any available media that can be accessedby processor(s) 510 and may include volatile media, non-volatile media,or both. The media may also be removable, non-removable, or both.

Additionally, computing system 500 includes a communication device 520,such as a transceiver, to provide access to a communications network viaa wireless and/or wired connection. In some embodiments, communicationdevice 520 may be configured to use Frequency Division Multiple Access(FDMA), Single Carrier FDMA (SC-FDMA), Time Division Multiple Access(TDMA), Code Division Multiple Access (CDMA), Orthogonal FrequencyDivision Multiplexing (OFDM), Orthogonal Frequency Division MultipleAccess (OFDMA), Global System for Mobile (GSM) communications, GeneralPacket Radio Service (GPRS), Universal Mobile Telecommunications System(UMTS), cdma2000, Wideband CDMA (W-CDMA), High-Speed Downlink PacketAccess (HSDPA), High-Speed Uplink Packet Access (HSUPA), High-SpeedPacket Access (HSPA), Long Term Evolution (LTE), LTE Advanced (LTE-A),802.11x, Wi-Fi, Zigbee, Ultra-WideBand (UWB), 802.16x, 802.15, HomeNode-B (HnB), Bluetooth, Radio Frequency Identification (RFID), InfraredData Association (IrDA), Near-Field Communications (NFC), fifthgeneration (5G), New Radio (NR), any combination thereof, and/or anyother currently existing or future-implemented communications standardand/or protocol without deviating from the scope of the invention. Insome embodiments, communication device 520 may include one or moreantennas that are singular, arrayed, phased, switched, beamforming,beamsteering, a combination thereof, and or any other antennaconfiguration without deviating from the scope of the invention.

Processor(s) 510 are further coupled via bus 505 to a display 525, suchas a plasma display, a Liquid Crystal Display (LCD), a Light EmittingDiode (LED) display, a Field Emission Display (FED), an Organic LightEmitting Diode (OLED) display, a flexible OLED display, a flexiblesubstrate display, a projection display, a 4K display, a high definitiondisplay, a Retina® display, an In-Plane Switching (IPS) display, or anyother suitable display for displaying information to a user. Display 525may be configured as a touch (haptic) display, a three dimensional (3D)touch display, a multi-input touch display, a multi-touch display, etc.using resistive, capacitive, surface-acoustic wave (SAW) capacitive,infrared, optical imaging, dispersive signal technology, acoustic pulserecognition, frustrated total internal reflection, etc. Any suitabledisplay device and haptic I/O may be used without deviating from thescope of the invention.

A keyboard 530 and a cursor control device 535, such as a computermouse, a touchpad, etc., are further coupled to bus 505 to enable a userto interface with computing system 500. However, in certain embodiments,a physical keyboard and mouse may not be present, and the user mayinteract with the device solely through display 525 and/or a touchpad(not shown). Any type and combination of input devices may be used as amatter of design choice. In certain embodiments, no physical inputdevice and/or display is present. For instance, the user may interactwith computing system 500 remotely via another computing system incommunication therewith, or computing system 500 may operateautonomously.

Memory 515 stores software modules that provide functionality whenexecuted by processor(s) 510. The modules include an operating system540 for computing system 500. The modules further include aninter-session automation module 545 that is configured to perform all orpart of the processes described herein or derivatives thereof. Computingsystem 500 may include one or more additional functional modules 550that include additional functionality.

One skilled in the art will appreciate that a “system” could be embodiedas a server, an embedded computing system, a personal computer, aconsole, a personal digital assistant (PDA), a cell phone, a tabletcomputing device, a quantum computing system, or any other suitablecomputing device, or combination of devices without deviating from thescope of the invention. Presenting the above-described functions asbeing performed by a “system” is not intended to limit the scope of thepresent invention in any way, but is intended to provide one example ofthe many embodiments of the present invention. Indeed, methods, systems,and apparatuses disclosed herein may be implemented in localized anddistributed forms consistent with computing technology, including cloudcomputing systems.

It should be noted that some of the system features described in thisspecification have been presented as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom verylarge scale integration (VLSI) circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, graphics processing units, or thelike.

A module may also be at least partially implemented in software forexecution by various types of processors. An identified unit ofexecutable code may, for instance, include one or more physical orlogical blocks of computer instructions that may, for instance, beorganized as an object, procedure, or function. Nevertheless, theexecutables of an identified module need not be physically locatedtogether, but may include disparate instructions stored in differentlocations that, when joined logically together, comprise the module andachieve the stated purpose for the module. Further, modules may bestored on a computer-readable medium, which may be, for instance, a harddisk drive, flash device, RAM, tape, and/or any other suchnon-transitory computer-readable medium used to store data withoutdeviating from the scope of the invention.

Indeed, a module of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within modules, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork.

Conventionally, in attended automation, human users wait while an RPArobot running in the same session completes its tasks. However, someembodiments create one or more robot sessions to host and run RPA robotstherein. Unlike existing RPA systems, users can benefit from the abilityto interact with their computing system while the robot(s) are runningautomations in the robot session(s). The user may still monitor what therobot is doing and interact with the robot through host automationwindow(s) for the robot session(s) in some embodiments. In someembodiments, the user and robot session(s) may be running on a remotemachine that is controlled by the user's computing system.

However, in some embodiments, the RPA robot does not interact withapplications that the user is using via the IPC facilitator. The RPArobot may instead interact with an application or other process that isnot visible to the user or is otherwise not being used by the user viathe RPA facilitator and RPA driver. Such robots typically do not augmentuser interactions with applications directly and may be considered to beunattended robots.

In certain embodiments, the RPA robot may be running on a user'scomputing system and driving a remote computing system through theremote runtime (e.g., via UiPath Remote Runtime™). UiPath RemoteRuntime™ is a component that facilitates the communication between aremote application or desktop, such as Citrix Virtual Apps andDesktops™, and the dedicated UiPath® extension (e.g., the UiPath®extension for Citrix® or the UiPath® extension for Windows® RemoteDesktop). UiPath Remote Runtime™ gathers information pertaining totargeted UI elements of remote applications and sends this informationto the corresponding extension so that selectors are natively generatedin UI Explorer™.

FIGS. 6A-G illustrate an example of completing a form in a user sessionusing an RPA robot running in a robot session, an IPC facilitator, andan RPA driver, according to an embodiment of the present invention. InFIG. 6A, a user session window 600 is shown, where a user is able tointeract with applications in the UI and no robot is currentlyexecuting. A robot tray icon 610 is visible in the lower right portionof user session window 600. An RPA driver 640 includes an IPCfacilitator 642 as a subprocess in this embodiment. However, in certainembodiments, IPC facilitator 642 may be a separate application orprocess that communicates with RPA driver 640 without deviating from thescope of the invention. In such embodiments, IPC facilitator 642 maycommunicate with RPA driver 640 via IPC, via API calls, etc. Indeed, incertain embodiments, IPC may not be used.

In FIG. 6B, the user launches a web browser and visits an invoicecreation web page 620. In FIG. 6C, the user pulls up a robot tray 612(e.g., by clicking robot tray icon 610) and selects a client sessionrobot option 614 to execute on his or her computing system. Afterselecting the robot to be executed, as shown in FIG. 6D, a robot sessionwindow 630 for a robot session appears as a child window on the screen.The RPA robot will operate in the robot session. In this embodiment, awindow 632 for the client session robot automatically launches withinrobot session window 630 and includes a button 634 for run a form fillerworkflow to retrieve data for web page 620 in the user session.

In some embodiments, the robot session window may not be displayed, andthe robot may launch, operate, and close automatically without beingvisible to the user. In certain embodiments, the robot may close itssession after completing its workflow. In some embodiments, rather thanlaunching from a robot tray, the robot session may be initiated and therobot may launch and operate without the use of robot tray 612 (e.g.,due to the user clicking a button in an application of the mainsession).

Turning to FIG. 6E, after the user clicks button 634, the robot beginsretrieving data for filling out form fields in web page 620. As therobot retrieves portions of the data, the data is sent to IPCfacilitator 642, which then causes RPA driver 640 to enter the data intoweb browser 620. For instance, RPA driver 640 may move the mouse over agiven field and cause the entry of text from the data into the field. InFIG. 6E, RPA driver 640 has already completed the Invoice Number fieldand has now moved the mouse to the Invoice Amount field, clicked on it,and entered the number 1. The caret appears after the number 1 in FIG.6E. In certain embodiments, RPA facilitator 642 may receive the completeset of data from robot 632 before causing RPA driver 640 to fill out thefields of web page 620.

Per the above, communication between the robot running in the robotsession and IPC facilitator 642 running in the user session isaccomplished using an IPC protocol. IPC protocols may facilitationcommunication via the network, pipes, Component Object Model (COM),Remote Procedure Calls (RPC), sockets, etc. Suitable session creationmechanisms and IPC protocols may be used for other operating systems aswell, where supported. The robot may send status notifications back toIPC facilitator 642 (e.g., indicating that the robot is starting,running, paused, etc.), retrieved data, error messages, commands, orother communications via the IPC protocol as well.

The associated text from the data retrieved by the robot is visible tothe user as it is entered by RPA driver 640 when web page 620 is notcovered by another window or minimized. While RPA driver 640 completesthe data interactions for the form, the user can interact with otherapplications and continue to be productive, or even interact with webpage 620 itself in some embodiments, although the user's entries may beoverwritten if RPA driver 640 modifies data for the same field that theuser entered information in.

Turning to FIG. 6F, after the robot completes its workflow, a message isdisplayed in window 632. As can be seen in the background, the robot hascompleted the data retrieval for the form fields, and the new entriesfor the form fields are visible in web page 620 after entry by RPAdriver 640. The user may then close out robot session window 630, therobot may close robot session window 630 (and potentially the robotsession itself) automatically, or robot session window 630 may stayopen. The user may then submit the completed form. See FIG. 6G.

FIGS. 7A-G illustrate an example of completing a form in a user sessionusing an RPA robot running in a robot session via direct variablemodification, according to an embodiment of the present invention. InFIG. 7A, a user session window 700 is shown, where a user is able tointeract with applications in the UI and no robot is currentlyexecuting. A robot tray icon 710 is visible in the lower right portionof user session window 700.

In FIG. 7B, the user launches a web browser and visits an invoicecreation web page 720. In FIG. 7C, the user pulls up a robot tray 712(e.g., by clicking robot tray icon 710) and selects a client sessionrobot option 714 to execute on his or her computing system. Afterselecting the robot to be executed, as shown in FIG. 7D, a robot sessionwindow 730 for a robot session appears as a child window on the screen.The RPA robot will operate in the robot session. In this embodiment, awindow 732 for the client session robot automatically launches withinrobot session window 730 and includes a button 734 for run a form fillerworkflow for web page 720 in the user session.

In some embodiments, the robot session window may not be displayed, andthe robot may launch, operate, and close automatically without beingvisible to the user. In certain embodiments, the robot may close itssession after completing its workflow. In some embodiments, rather thanlaunching from a robot tray, the robot session may be initiated and therobot may launch and operate without the use of robot tray 712 (e.g.,due to the user clicking a button in an application of the mainsession).

Turning to FIG. 7E, after the user clicks button 734, the robot beginsfilling out form fields in web page 720 by accessing and interactingwith variables for the form fields of web page 720. For instance, therobot may change memory values for the fields stored in RAM, permanentlocal storage, a database, or any other storage type and/or locationwithout deviating from the scope of the invention. In certainembodiments, the variables may be stored as part of the memory allocatedfor and used by the web application associated with web form 720.

The respective memory values changed by the robot cause the respectivefields of web page 720 to be updated when web page 720 is refreshed. Theassociated text changed by the robot via the data modifications isvisible to the user when web page 720 is not covered by another windowor minimized. Unlike the example in FIGS. 6A-G, where RPA driver 640manipulates the mouse and enters the text via API level and/or nativemechanisms, data appears in the form fields of web page 720 without suchinteractions. While the robot completes the data interactions for theform, the user can interact with other applications and continue to beproductive, or even interact with web page 720 itself in someembodiments, although the user's entries may be overwritten if the robotmodifies data for the same field that the user entered information in.

Turning to FIG. 7F, after the robot completes its workflow, a message isdisplayed in window 732. As can be seen in the background, the robot hascompleted the data modifications for the respective memory variablesassociated with the form fields, and the new entries for the form fieldsare visible in web page 720 after it refreshes. The user may then closeout robot session window 730, the robot may close robot session window730 (and potentially the robot session itself) automatically, or robotsession window 730 may stay open. The user may then submit the completedform. See FIG. 7G.

In some embodiments, the robot session may be a child session, and thechild session may be created via a child session API of the operatingsystem. Windows® Terminal Services Child Sessions or another childsession API provided by an operating system may be used in someembodiments to create the second session without deviating from thescope of the invention. The robot tray application (e.g., the UiPath®Robot Agent Desktop) or another application configured to launchrobot(s) may then use the create process APIs in the operating systemwith the appropriate arguments to start the robot process in that childsession. The robot tray application or other suitable application maythen communicate with the robot process using a suitable protocol (e.g.,one built on named pipes).

FIG. 8 is a flowchart illustrating a process 800 for automation of aprocess running in a user session via an RPA robot running in a robotsession, an IPC facilitator, and an RPA driver, according to anembodiment of the present invention. The process begins with launching auser session window at 810. This may be the main window associated withthe operating system running on the user computing system, for example.A robot session window is then launched as a child window of the usersession window at 820. In some embodiments, the robot session window maybe launched responsive to the robot being initiated or otherwiselaunched, for example. The robot is then initiated in the robot sessionat 830.

The robot is executed at 840 and communicates with an IPC facilitatorvia IPC. The IPC facilitator may receive status notifications, retrieveddata, error messages, commands, or other communications from the robotvia IPC. The IPC facilitator may also send messages to the robot (suchas commands, status updates, error messages from the IPC facilitator orRPA driver, etc.).

Using the data retrieved from the robot, the RPA facilitator controls orotherwise causes the RPA driver to perform application interactionsusing the retrieved data and/or other communications from the robot at850. For instance, the RPA driver may be caused to move the mouse, clickon fields, enter text, click a button, navigate a menu, open or closeand application or window, etc. After the robot completes its execution,the robot session may be ended and the robot session window may beclosed automatically in some embodiments at 860.

FIG. 9 is a flowchart illustrating a process 900 for automation of aprocess running in a user session via an RPA robot running in a robotsession via direct variable modification, according to an embodiment ofthe present invention. The process begins with launching a user sessionwindow at 910. This may be the main window associated with the operatingsystem running on the user computing system, for example. A robotsession window is then launched as a child window of the user sessionwindow at 920. In some embodiments, the robot session window may belaunched responsive to the robot being initiated or otherwise launched,for example. The robot is then initiated in the robot session at 930 andthe robot interacts with data associated with application(s) (e.g., webpages, spreadsheets, ERP applications, sales applications, etc.) runningin the user session from the robot session at 940. For instance, therobot may create, change, or delete stored information in computingsystem memory to cause the changes to occur in the common stored data,which is accessed and used by the application(s) in the user session.After the robot completes its execution, the robot session may be endedand the robot session window may be closed automatically in someembodiments at 950.

In some embodiments, multiple running automation processes (e.g., UIautomation processes) may be isolated in the client session. This mayallow these processes to be called on demand from the main session viaIPC, for example. In this manner, multiple RPA robot processes may beavailable on demand to be called from a main session application, a mainsession RPA robot, another client session RPA robot, etc. RPA robotsrunning in the client session may also be able to collect data from themain session. In certain embodiments, RPA robots running in the clientsession may wait for a certain trigger from the main session before theyperform their automation or part of an automation.

FIG. 10 is an architectural diagram 1000 illustrating an example ofmultiple client session RPA robots interacting with a main sessionapplication, according to an embodiment of the present invention. InFIG. 10, a main session 1010 and a client session 1020 are running.Client session 1020 includes client session RPA robot 1 1030 and clientsession RPA robot 2 1032.

Client session RPA robots 1030, 1032 communicate with a separate IPCfacilitator application 1040 or embedded RPA facilitator process orsubroutine 1052 that is part of driver 1050. In some embodiments, driver1050 may be driver 340 of FIG. 3, for example. IPC facilitator 1040 or1052 causes driver 1050 to interact with a main session applicationand/or an associated application object 1060 (e.g., a Component ObjectModel (COM) object for a Microsoft Windows® application) in the mannerdictated by the respective workflow logic of client session RPA robot1030 or 1032. For instance, driver 1050 may be caused to move a mouse,fill out form data, click one or more buttons, interact with a menu, acombination thereof, etc. in main session application 1060. In certainembodiments, RPA facilitator application 1040 may communicate with mainsession application and/or associated application object 1060 directly.

In certain embodiments, RPA robots running in the client session may beattended automation robots. For instance, an RPA robot running in theclient session may ask for input from a user in the main session. Thismay be accomplished via IPC with a main session robot, a driver, etc.

FIG. 11 is a flow diagram 1100 illustrating a process for running anattended automation RPA robot in a client session, according to anembodiment of the present invention. In this embodiment, the userutilizes a main session application 1110 that causes a client sessionRPA robot process to start via IPC at 1120. In some embodiments, mainsession application 1110 may be an RPA assistant application that allowsa user in the main session to interact with the attended RPA robot inthe client session. For example, a dashboard of the RPA assistantapplication may show the current RPA processes supported by the robot,and the user can select a process to be executed. In certainembodiments, the RPA assistant application may display the steps of theclient session workflow and/or execution status while the client sessionRPA robot is running.

After the client session RPA robot starts at 1120, the client sessionRPA robot runs a first part of its logic at 1130. After execution of thefirst part of the logic at 1130, the client session RPA robot asks foruser input at 1140. This can occur via a message in an applicationrunning in the main session that appears via an IPC facilitator anddriver interacting with the main session application, a message from anRPA robot running in the main session, etc. The user then provides therequested input, which is sent to the client session RPA robot via IPC,and the second part of the logic is executed at 1150 using this input.After the client session RPA robot process ends at 1160, main sessionapplication 1110 may receive a notification that the RPA robot processhas ended.

In certain embodiments, parts of an automation may be run in the mainsession and other parts of the automation may be run in the clientsession. For instance, a main session application or RPA robot mayperform certain operations in the main session and then cause an RPArobot running in the client session to execute another part of theautomation when the main session application or robot reaches a certainpoint in its execution, receives a trigger, a logical condition issatisfied, etc. The client session RPA robot can perform its part of theautomation sequentially or in parallel with the main session applicationor robot. The client session RPA robot can then provide an indication,requested data, execution results, etc. to the main session applicationor robot.

FIG. 12 is a flow diagram 1200 illustrating execution of a multi-robotcollective workflow between a main session robot M1, a client sessionapplication A1, and a pair of client session robots C1 and C2, accordingto an embodiment of the present invention. A1, C1, and/or C2 may be inthe same client session or different client sessions. M1 beginsexecuting its workflow and reaches an activity that calls for C1 tocomplete a workflow. This may be performed by an “invoke workflow”activity that has a flag set to execute the RPA process in the clientsession in some embodiments. M1 causes C1 to execute its workflow viaIPC and the calling activity waits. During this time, M1 may performother tasks in some embodiments.

After C1 completes its workflow, C1 notifies M1 via IPC, and M1 resumesexecution until it reaches an activity that calls for A1, which is aprocess in the client session, to begin executing or to complete a task.M1 causes A1 to execute and/or to perform a task via IPC and the callingactivity (e.g., an “invoke process” activity) waits. An invoke processactivity may have a flag set to execute A1 in the client session in someembodiments. Once again, M1 may perform other tasks while waiting for A1in some embodiments.

After A1 completes its process or task, A1 notifies M1 via IPC, and M1resumes execution until it reaches an activity that calls for C2 tocomplete a workflow. M1 causes C2 to execute its workflow via IPC andthe calling activity waits. Once again, M1 may perform other tasks whilewaiting for C2 in some embodiments.

After C2 completes its workflow, M1 is notified via IPC and resumesexecution until it reaches an activity that once again calls for C1 tocomplete a workflow. This may be the same workflow activities aspreviously executed or a different workflow or set of activities. M1causes C1 to execute its workflow via IPC and the calling activitywaits. Yet again, M1 may perform other tasks while waiting for C1 insome embodiments. After C1 completes its workflow, M1 is notified viaIPC resumes execution until the workflow of M1 is completed. In certainembodiments, C1 may remain running after being initially invoked and maystill be running when called again by M1.

Per the above, in some embodiments, M1 may include one or more “invokeworkflow” activities and/or an “invoke process” activities that mayinvoke RPA robot(s) (e.g., C1 and/or C2) and/or other processes (e.g.,A1) in the client session. Such an activity may start the respective RPArobot(s) and/or process(es), communicate with RPA robot(s) and/orprocess(es) that are already running, etc. These activities may becreated when an RPA developer develops the workflow for M1. In certainembodiments, RPA robot(s) may invoke RPA robots and/or processes fromthe client session into the main session via an RPA facilitator or othersuitable functionality.

During execution, M1 may communicate with A1, C1, and C2 via IPC, andvice versa. For instance, M1 may send comments and requests to A1, C1,and C2, M1 may receive status messages, results, and error messages fromA1, C1, and C2, etc. In this manner, M1 may act as a main RPA robot thatcontrols client session RPA robots and/or other processes (e.g.,applications) in the client session. In certain embodiments, M1, A1, C1,and/or C2 may operate in parallel.

In some embodiments, M1 may perform all interactions with applicationsrunning in the main session, which may eliminate the need for an IPCfacilitator. Thus, C1 and C2 may perform various data retrieval andprocessing tasks and M1 may perform UI interaction tasks. In certainembodiments, at least some workflow activities of M1, C1, and/or C2 maybe executed in parallel. One such example is shown in flow diagram 1300of FIG. 13, where C1 is executed based on the logic of M1 and executionoccurs in parallel. Communications may be sent between M1 and C1 duringthe section of C1. However, in certain embodiments, C1 may complete itsexecution independently, and may complete execution of its workflowafter M1 ends.

In some embodiments, all RPA robot activities run in the client session.RPA robots may be called from the main session by a robot executor, forinstance, such as the UiPath® robot tray, an IPC facilitator, anotherapplication, etc. Results of the execution of the RPA robots and othercommunications could be provided to the robot executor or otherapplication via IPC.

In certain embodiments, a standardized communication format may be usedfor IPC communications between the client session and the main session.For instance, main session and client session processes may exchangeXAML data. This helps to ensure that communications are in a format thatthe respective processes can recognize.

In some embodiments, IPC may be used between RPA processes running inthe same session for synchronization purposes. For instance, multipleRPA processes may run in parallel in the background with a foregroundprocess in a main session. IPC may provide a synchronization mechanismto exchange information between the background processes and theforeground or main process.

In certain embodiments, the driver (e.g., driver 340 of FIG. 3) will beloaded in a main RPA workflow process. The communication between thechild RPA process and the main RPA workflow process may occur via IPC.This allows the main RPA workflow process to utilize the driver to carryout operations for the client session robot based on IPC information.

In some embodiments, a client session RPA robot may work withapplications open in the main session. For instance, a client sessionRPA robot may work with an Excel® spreadsheet open in the main session.This can occur via IPC between the client session RPA robot and an RPAfacilitator, for example. The RPA facilitator may cause the driver tocarry out the interaction(s) with the Excel® spreadsheet based oninformation provided by the client session RPA robot (e.g., enteringdata into a spreadsheet, modifying table values, etc.). In certainembodiments, activities may be included in an RPA workflow thatautomatically capture application data between both sessions (e.g.,Microsoft Office® activities, web browser activities, etc.). In thismanner, the client session RPA robot essentially works with applicationsrunning in the main session as if they are running in the RPA robot'sown session. Indeed, in some embodiments, an RPA developer may not beaware that workflows or parts thereof that he or she is developing willbe executed in the client session.

In certain embodiments, when designing an RPA robot using a designerapplication, for example, the RPA developer may set a client sessionflag on an “invoke workflow” activity or an “invoke process” activity.The invoke workflow activity invokes an RPA workflow. The invoke processactivity executes a process that is available for the local machine.Setting this flag may cause the RPA workflow or process to be invoked inthe client session rather than the main session.

In some embodiments, the execution of the client session RPA robot maybe based on a trigger from a main session application and/or RPA robot.FIG. 14 is a flow diagram 1400 illustrating execution of a clientsession RPA robot based on a trigger for a main session application,according to an embodiment of the present invention. A main sessionapplication A1 (which may be an RPA robot in some embodiments) beginsexecuting and waits for a trigger. After the trigger is received, A1starts execution of a client session RPA robot C1 via IPC.Communications may be sent between A1 and C1 during the section of C1.A1 then waits for another trigger and C1 executes its workflow.

FIG. 15 is a flowchart illustrating a process 1500 for performinginter-session automation, according to an embodiment of the presentinvention. The process begins with executing an RPA robot in a mainsession of a computing system at 1510. an RPA robot or an application iscalled or launched in a client session via IPC by the main session RPArobot at 1520. Messages are communicated between the client session RPArobot or application and the main session RPA robot via IPC at 1530. Insome embodiments, the main session RPA robot pauses its execution untilthe execution of the client session RPA robot or application ends at1540.

Result(s) of the execution of the client session RPA robot orapplication are received via IPC by the main session RPA robot at 1550.The main session RPA robot then uses the result(s) at 1560 to completeat least a portion of the workflow of the main session RPA robot, tointeract with an application or application object running in the mainsession, or both. In some embodiments, the process is repeated for thenext client session RPA robot or client session application at 1570, andthe process returns to step 1520.

In some embodiments, the client session RPA robot, the client sessionapplication, or both, are called or launched two or more times in theworkflow of the main session RPA robot. In certain embodiments, theclient session application is called or launched via an invoke processactivity of the workflow of the main session RPA robot, the clientsession RPA robot is called or launched via an invoke workflow activityof the workflow of the main session RPA robot, or both. In someembodiments, the invoke process activity comprises a flag indicatingthat the client session application is run in the client session, theinvoke workflow activity comprises a flag indicating that the clientsession RPA robot is run in the client session, or both. In certainembodiments, the client session application, the client session RPArobot, or both, continue running after providing the results. In someembodiments, the IPC communications between the main session RPA robotand the client session RPA robot and/or client session application arein a standardized communication format.

The process steps performed in FIGS. 8-15 may be performed by a computerprogram, encoding instructions for the processor(s) to perform at leastpart of the process(es) described in FIGS. 8-15, in accordance withembodiments of the present invention. The computer program may beembodied on a non-transitory computer-readable medium. Thecomputer-readable medium may be, but is not limited to, a hard diskdrive, a flash device, RAM, a tape, and/or any other such medium orcombination of media used to store data. The computer program mayinclude encoded instructions for controlling processor(s) of a computingsystem (e.g., processor(s) 510 of computing system 500 of FIG. 5) toimplement all or part of the process steps described in FIGS. 8-15,which may also be stored on the computer-readable medium.

The computer program can be implemented in hardware, software, or ahybrid implementation. The computer program can be composed of modulesthat are in operative communication with one another, and which aredesigned to pass information or instructions to display. The computerprogram can be configured to operate on a general purpose computer, anASIC, or any other suitable device.

It will be readily understood that the components of various embodimentsof the present invention, as generally described and illustrated in thefigures herein, may be arranged and designed in a wide variety ofdifferent configurations. Thus, the detailed description of theembodiments of the present invention, as represented in the attachedfigures, is not intended to limit the scope of the invention as claimed,but is merely representative of selected embodiments of the invention.

The features, structures, or characteristics of the invention describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, reference throughout thisspecification to “certain embodiments,” “some embodiments,” or similarlanguage means that a particular feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment of the present invention. Thus, appearances of the phrases“in certain embodiments,” “in some embodiment,” “in other embodiments,”or similar language throughout this specification do not necessarily allrefer to the same group of embodiments and the described features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

It should be noted that reference throughout this specification tofeatures, advantages, or similar language does not imply that all of thefeatures and advantages that may be realized with the present inventionshould be or are in any single embodiment of the invention. Rather,language referring to the features and advantages is understood to meanthat a specific feature, advantage, or characteristic described inconnection with an embodiment is included in at least one embodiment ofthe present invention. Thus, discussion of the features and advantages,and similar language, throughout this specification may, but do notnecessarily, refer to the same embodiment.

Furthermore, the described features, advantages, and characteristics ofthe invention may be combined in any suitable manner in one or moreembodiments. One skilled in the relevant art will recognize that theinvention can be practiced without one or more of the specific featuresor advantages of a particular embodiment. In other instances, additionalfeatures and advantages may be recognized in certain embodiments thatmay not be present in all embodiments of the invention.

One having ordinary skill in the art will readily understand that theinvention as discussed above may be practiced with steps in a differentorder, and/or with hardware elements in configurations which aredifferent than those which are disclosed. Therefore, although theinvention has been described based upon these preferred embodiments, itwould be apparent to those of skill in the art that certainmodifications, variations, and alternative constructions would beapparent, while remaining within the spirit and scope of the invention.In order to determine the metes and bounds of the invention, therefore,reference should be made to the appended claims.

1. A computer-implemented method, comprising: receiving one or moremessages from a client session robotic process automation (RPA) robotvia inter-process communication (IPC), by a main session RPA robot; andusing results from the received one or more messages from the clientsession RPA robot to complete at least a portion of a workflow of themain session RPA robot, to interact with an application or applicationobject running in the main session, or both, by the main session RPArobot.
 2. The computer-implemented method of claim 1, furthercomprising: calling or launching an application in the client sessionvia IPC, by the main session RPA robot; receiving one or more messagesfrom the client session application via IPC during and/or afterexecution of a task of the application, by the main session RPA robot;and using results from the received one or more messages from the clientsession application to complete at least a portion of the workflow ofthe main session RPA robot, to interact with the application orapplication object running in the main session, or both, by the mainsession RPA robot.
 3. The computer-implemented method of claim 2,further comprising: pausing execution of the main session RPA robotuntil the client session application completes execution.
 4. Thecomputer-implemented method of claim 2, wherein the client sessionapplication is called or launched two or more times in the workflow ofthe main session RPA robot.
 5. The computer-implemented method of claim2, further comprising: calling or launching an additional application inthe client session via IPC, by the main session RPA robot; receiving oneor more messages from the additional client session application via IPC;and using results from the received one or more messages from theadditional client session application to complete a portion of theworkflow of the main session RPA robot, to interact with the applicationor application object running in the main session, or both, by the mainsession RPA robot.
 6. The computer-implemented method of claim 2,wherein the client session application is called or launched via aninvoke process activity of the workflow of the main session RPA robot.7. The computer-implemented method of claim 2, wherein the IPCcommunications between the main session RPA robot and the client sessionapplication are in a standardized communication format.
 8. Thecomputer-implemented method of claim 2, wherein the main session RPArobot is configured to listen for IPC messages from the client sessionapplication, send communications to and receive communications from theclient session application, monitor an execution status of the clientsession application, or any combination thereof.
 9. Thecomputer-implemented method of claim 1, further comprising: pausingexecution of the main session RPA robot until the client session RPArobot completes execution.
 10. The computer-implemented method of claim1, further comprising: calling or launching an additional RPA robot inthe client session via IPC, by the main session RPA robot; receiving oneor more messages from the additional client session RPA robot via IPC;and using results from the received one or more messages from theadditional client session RPA robot to complete a portion of theworkflow of the main session RPA robot, to interact with the applicationor application object running in the main session, or both, by the mainsession RPA robot.
 11. The computer-implemented method of claim 1,wherein the client session RPA robot is called or launched two or moretimes in the workflow of the main session RPA robot.
 12. Thecomputer-implemented method of claim 1, wherein the client session RPArobot is called or launched via an invoke workflow activity of theworkflow of the main session RPA robot.
 13. The computer-implementedmethod of claim 12, wherein the invoke workflow activity comprises aflag indicating that the client session RPA robot is run in the clientsession.
 14. The computer-implemented method of claim 1, wherein theclient session RPA robot continues running after the results areprovided to the main session RPA robot.
 15. The computer-implementedmethod of claim 1, wherein the IPC communications between the mainsession RPA robot and the client session RPA robot are in a standardizedcommunication format.
 16. The computer-implemented method of claim 1,wherein the main session RPA robot is configured to listen for IPCmessages from the client session RPA robot, send communications to andreceive communications from the client session RPA robot, monitor anexecution status of the client session RPA robot, or any combinationthereof.
 17. A non-transitory computer-readable medium storing acomputer program, the computer program configured to cause at least oneprocessor to: call or launch an application in a client session viainter-process communication (IPC), by a main session robotic processautomation (RPA) robot; receive one or more messages from the clientsession application via IPC, by the main session RPA robot; and useresults from the received one or more messages from the client sessionapplication to complete at least a portion of a workflow of the mainsession RPA robot, to interact with an application or application objectrunning in the main session, or both, by the main session RPA robot. 18.The non-transitory computer-readable medium of claim 17, wherein thecomputer program is further configured to cause the at least oneprocessor to: pause execution of the main session RPA robot until theclient session application completes execution.
 19. The non-transitorycomputer-readable medium of claim 17, wherein the computer program isfurther configured to cause the at least one processor to: receive oneor more messages from an additional client session application via IPC;and use results from the received one or more messages from theadditional client session application to complete a portion of theworkflow of the main session RPA robot, to interact with the applicationor application object running in the main session, or both, by the mainsession RPA robot.
 20. The non-transitory computer-readable medium ofclaim 17, wherein the client session application is called or launchedvia an invoke process activity of the workflow of the main session RPArobot.
 21. The non-transitory computer-readable medium of claim 20,wherein the invoke process activity comprises a flag indicating that theclient session application is run in the client session.
 22. Thenon-transitory computer-readable medium of claim 17, wherein the clientsession application continues running after the task is completed. 23.The non-transitory computer-readable medium of claim 17, wherein themain session RPA robot is configured to listen for IPC messages from theclient session application, send communications to and receivecommunications from the client session application, monitor an executionstatus of the client session application, or any combination thereof.24. A computing system, comprising: memory storing computer programinstructions; and at least one processor configured to execute thecomputer program instructions, wherein the computer program instructionsare configured to cause at least one processor to: call or launch arobotic process automation (RPA) robot in a client session viainter-process communication (IPC), by a main session RPA robot; call orlaunch an application in the client session via IPC, by the main sessionRPA robot; receive one or more messages from the client session RPArobot and the client session application via IPC, by the main sessionRPA robot; and use results from the received one or more messages fromthe client session RPA robot and the client session application tocomplete at least a portion of a workflow of the main session RPA robot,to interact with one or more applications and/or application objectsrunning in the main session, or both, by the main session RPA robot. 25.The computing system of claim 24, the computer program instructions arefurther configured to cause the at least one processor to: pauseexecution of the main session RPA robot until the client session RPArobot, the client session application, or both, complete execution. 26.The computing system of claim 24, wherein the client sessionapplication, the client session application, or both, are called orlaunched two or more times in the workflow of the main session RPArobot.
 27. The computing system of claim 24, wherein the computerprogram instructions are further configured to cause the at least oneprocessor to: call or launch an additional application, an additionalRPA robot, or both, in the client session via IPC, by the main sessionRPA robot; receive one or more messages from the additional clientsession application, the additional RPA robot, or both, via IPC; and useresults from the received one or more messages from the additionalclient session application, the additional client session RPA robot, orboth, to complete a portion of the workflow of the main session RPArobot, to interact with at least one of the one or more applicationsand/or application objects running in the main session, or both, by themain session RPA robot.
 28. The computing system of claim 24, whereinthe client session application is called or launched via an invokeprocess activity of the workflow of the main session RPA robot, theclient session RPA robot is called or launched via an invoke workflowactivity of the workflow of the main session RPA robot, or both.
 29. Thecomputing system of claim 28, wherein the invoke process activitycomprises a flag indicating that the client session application is runin the client session, the invoke workflow activity comprises a flagindicating that the client session RPA robot is run in the clientsession, or both.
 30. The computing system of claim 24, wherein the mainsession RPA robot is configured to listen for IPC messages from theclient session application and the client session RPA robot, sendcommunications to and receive communications from the client sessionapplication and the client session RPA robot, monitor an executionstatus of the client session application and the client session RPArobot, or any combination thereof.